kueue: Assign release priority to internal-pipelinerun child pipelines (production base) #10310
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arewm The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
🤖 Gemini AI Assistant AvailableHi @arewm! I'm here to help with your pull request. You can interact with me using the following commands: Available Commands
How to Use
PermissionsOnly OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage. This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance. |
|
🤖 Hi @arewm, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
Child pipelines created by internal-pipelinerun (such as signing pipelines) were receiving the default priority (400) instead of release priority (1000). This caused them to be blocked behind multi-arch build pipelines waiting for ppc64le/s390x capacity, even though signing pipelines don't require those resources. Add a CEL rule to recognize pipelines with the internal-services.appstudio.openshift.io/pipelinerun-uid label and assign them konflux-release priority, matching their parent managed release pipelines. Assisted-by: Claude Code (Opus 4.5)
arewm
force-pushed
the
kueue-internal-pipelinerun-priority-prod
branch
from
c1f7932 to
8fe7485
Compare
arewm
changed the title
| plrNamespace == 'mintmaker' ? priority('konflux-dependency-update') : | ||
| has(pipelineRun.metadata.labels) && |
There was a problem hiding this comment.
Need to update the test for this pr as well
2 participants
Summary
internal-services.appstudio.openshift.io/pipelinerun-uidlabelkonflux-releasepriority, matching their parent managed release pipelinesBackground
Child pipelines created by internal-pipelinerun (such as signing pipelines) were receiving the default priority (400) instead of release priority (1000). This caused them to be blocked behind multi-arch build pipelines waiting for ppc64le/s390x capacity, even though signing pipelines don't require those resources.
🤖 Generated with Claude Code